Skip to content

Upgrade to otel sdk v2 #1789

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

wpessers
Copy link
Contributor

@wpessers wpessers commented Apr 23, 2025

Still work in progress. Most of it should be covered by this PR, but still doing some smoke-testing on my own lambdas

@wpessers wpessers marked this pull request as ready for review May 3, 2025 14:40
@wpessers wpessers requested a review from a team as a code owner May 3, 2025 14:40
@rndD
Copy link
Contributor

rndD commented May 8, 2025

Hi @wpessers, any plans to merge it soon?

@wpessers
Copy link
Contributor Author

wpessers commented May 8, 2025

@rndD I will be doing some final testing tonight hopefully. Things should move quickly from there. But be aware that I can't guarantee when the next version for the layer will be released, this might take some time still after the PR has been merged.

@rndD
Copy link
Contributor

rndD commented May 8, 2025

@wpessers, thanks for the detailed answer.

Can you tell me the current cycle or strategy for layer releases?

@wpessers
Copy link
Contributor Author

wpessers commented May 8, 2025

@wpessers, thanks for the detailed answer.

Can you tell me the current cycle or strategy for layer releases?

I will have to refer you to @serkan-ozal @tylerbenson @pragmaticivan for this question. As far as I'm aware there's no strict release cycle. It's just that when we are ready to release a certain change for a language specific layer, we want to make sure to also include "low-hanging fruit" (like dependency upgrades) for the different language-specific layers.

And if there happens to be some change in another layer that we want to release, this may hold back the entire release a little bit. So that we don't have to do multiple releases after one another in a short period of time.

@serkan-ozal serkan-ozal merged commit 0b2e564 into open-telemetry:main May 9, 2025
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants